-
Notifications
You must be signed in to change notification settings - Fork 184
Pass resourceType instead of resourceIndex to resourceSharingClient #4333
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Craig Perkins <[email protected]>
Signed-off-by: Craig Perkins <[email protected]>
Signed-off-by: Craig Perkins <[email protected]>
Signed-off-by: Craig Perkins <[email protected]>
|
CI failed not related to code changes |
|
@cwperks can you look at this test and try reproduce locally? |
looking, a few min |
Signed-off-by: Craig Perkins <[email protected]>
|
@mingshl pushed a commit to fix that test suite..my bad. I missed 2 instances to update. |
|
@peterzhuamazon can we override and merge? Couple integ test suites have passed already. This is blocking development. |
Merged. |
Description
This PR is related to the changes in opensearch-project/security#5713 to support multiple resource types in the same index. There's a small change in all ResourceSharingClient methods to accept type in the place of index.
resource type <-> resource index is a many-to-one relationship (think dashboards saved objects where multiple saved object types are in the same index).
On another note, ResourceSharingClient is used in instances where a mechanism doesn't currently exist as in parent<->child relationships (like a detector and results where all results are associated with a detector). Security is working on a mechanism to support this natively to obviate the need for ResourceSharingClient and instead abstract all the logic behind-the-scenes to the security plugin.
Check List
--signoff.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.